Fix 128kb url limit in open_config_page #3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There is a 128kb hard coded limit by default in the linux kernel for the max length of a single argument (MAX_ARG_STRLEN).
The
open_config_page()
function in theBrowserController
object can run into this if the generated app configuration URL is sufficiently large. This is because the webbrowser module will just pass the provided URL as a command line argument to the selected browser.This can be worked around by writing the url out to a temporary file instead and wrapping it in a client side redirect (
<meta http-equiv="refresh" content="0;url={}/>
).I wrote a small script to show the error and prove my solution:
The contents of the test url (
url.txt
) are ~145kb large:url.txt
Output before changing
open_config_page
:Output after switching over to the tempfile method:
The browser then proceeds to open the configuration page: